CI: install cln specific pyln packages in uv frameworks #702
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daywalker90
force-pushed
the
uv-use-matching-pyln
branch
from
0d36112 to
fbcaad5
Compare
|
had to upgrade to 25.02.2 since there is no pyln-proto package for 25.02, so why not 25.09.1 aswell |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I forgot to use CLN specific
pyln-*versions which breaks tests as soon as an incompatible combo is used (e.g. in #701)This fixes it by adding the specific pyln versions when a uv framework is detected by running
uv addwhich overrides the version specified by the plugin repo and for nightly we add the local path as an editable source.